Crawlee v4's `EventManager` constructor now requires
`EventManagerOptions` (just `persistStateIntervalMillis`), and the
base class no longer carries a `config` field — the previous
`override readonly config` pattern is no longer valid.

- Drop the `override` and store `config` as own readonly property.
- Forward `persistStateIntervalMillis` to `super()`.
- Add a `fromConfig()` factory mirroring `LocalEventManager.fromConfig()`
  so the SDK plays nicely with the new ServiceLocator-driven init path.

Stacked on #583 (config redesign); rebases onto v4 once that lands.

`Configuration.useEventManager()` was removed in crawlee v4. Install
the platform event manager via the global service locator instead, and
reset between tests so each case can register a fresh manager without
hitting `ServiceConflictError`.

Crawlee v4's `Configuration` is eager — `actorEventsWsUrl` is read
once at construction, so a global config that pre-existed the
`beforeEach` would never see the websocket URL we set, and
`events.init()` would silently never connect. Move the env-var setup
above `Configuration.getGlobalConfig()` and reset the SDK's static
singleton so each test rebuilds a fresh config.

…late

…anup

Crawlee v4 reshaped its `StorageClient` interface (async factory
methods that accept `id` *or* `name`), removed the cached
`storageObject` from `KeyValueStore`, and made `getPublicUrl` async.
The existing SDK code targeted the v3 shape and no longer compiles.

Changes:
- New `ApifyStorageClient` adapter wraps `apify-client`'s legacy
  `dataset()/keyValueStore()/requestQueue()` accessors and exposes
  the `createDatasetClient/createKeyValueStoreClient/createRequestQueueClient`
  factories crawlee now expects. Names are resolved to IDs via the
  collection `getOrCreate(name)` calls. apify-client's resource
  clients don't yet implement v4-only members like `getMetadata` /
  `getRecordPublicUrl`; the adapter casts through with a TODO
  comment so the structural alignment can land separately upstream.
- `Actor.init` and `_openStorage` now wrap `this.apifyClient` in
  `ApifyStorageClient` before handing it to crawlee.
- `KeyValueStore.getPublicUrl` is now async; the per-store
  `urlSigningSecretKey` is fetched on demand via the (private)
  `client.getMetadata()` instead of the removed `storageObject`
  cache. URL-signing behaviour for platform-mode reads is preserved.
- `Actor.openRequestQueue` reads `totalRequestCount` via the new
  `client.getMetadata()` (the old `client.get()` was dropped).
- `StorageManager.openStorage` is now `(class, id?, client?)` —
  removed the trailing `this.config` argument.

Stacked on #583 (config redesign); rebases onto v4 once that lands.

Replace the removed `StorageManager.clearCache()` and
`Configuration.useStorageClient()` with `serviceLocator.reset()`
plus `serviceLocator.setStorageClient()`.

…n emulator init/destroy

…apter

- `openRequestQueue should open storage`: mock client uses
  `getMetadata()` (the v3 `get()` was dropped on
  RequestQueueClient).
- Both Storage API tests assert that StorageManager.openStorage is
  called with an ApifyStorageClient (matched structurally) instead of
  the raw ApifyClient — the SDK now wraps it for crawlee v4.

Actor.init() calls Configuration.storage.enterWith(this.config), which
sticks the resolved config onto the current async context and persists
across tests on Node 22 (but not Node 24+). The cached value short-
circuits Configuration.getGlobalConfig() so subsequent tests never see
the env vars they just set.

Reset the AsyncLocalStorage value alongside the other singletons in
the test emulator so addWebhook (and friends) see ACTOR_RUN_ID etc.

…eset

`Actor.init()` calls `Configuration.storage.enterWith(this.config)`,
which sets the AsyncLocalStorage value on whichever async context the
test runner happened to be on. `enterWith(undefined)` from a child
async branch (vitest's beforeEach) doesn't unwind that — on Node 22
the test body re-enters a sibling context where the original
`enterWith` is still in effect, so `getStore()` still returns the
stale Configuration even after our reset.

Swapping the entire `AsyncLocalStorage` instance for a fresh one
guarantees `getStore()` returns `undefined` for every async branch
that follows, fixing the addWebhook test failures on Node 22.

…f inline boilerplate